home *** CD-ROM | disk | FTP | other *** search
- README.TXT file for the Setup Toolkit SETUP.EXE version 1.00.004
- ----------------------------------------------------------------
- This file lists the changes made to SETUP.EXE after Visual Basic
- version 3.0 shipped. The version of SETUP.EXE that was released with
- Visual Basic version 3.0 has a date and time of 28-APR-1993 12:00 am
- and is 15312 bytes in size. The file contains no version number.
-
- Installation Notes
- ------------------
- Copy this version of SETUP.EXE into your SETUPKIT\KITFILES directory
- over your existing copy of SETUP.EXE.
-
- Distribution Notes
- ------------------
- You are free to distribute this version of SETUP.EXE royalty free.
-
- Features/Bug Fixes
- ------------------
- The following are the features and bug fixes that were added to
- SETUP.EXE after VB 3.0 was released. This file will be updated with
- the latest bug fixes and features any time a new post-release VB 3.0
- version of SETUP.EXE becomes available.
-
- Version Bug Fix/Feature Comments
- ---------------------------------------------------------------------
- 1.00.002 VER.DLL is truncated to SETUP.EXE now checks to see
- zero bytes if it is not if VER.DL_ exists on your
- found or has an incorrect distribution disk. If it is
- name on the distribution not found, the following error
- disk. error is displayed and then
- SETUP.EXE terminates:
- "Error - File not found:
- A:\VER.DL_. This file is
- required by Setup."
-
- 1.00.002 SETUP.EXE does not run When running SETUP.EXE in
- in Windows version 3.0. Microsoft Windows version 3.0,
- you will receive the error "This
- application requires a newer
- version of Windows." This error
- causes SETUP.EXE to terminate.
- This bug has been fixed so that
- SETUP.EXE will run successfully
- in Microsoft Windows version
- 3.0.
-
- 1.00.002 The Visual Basic version This problem occurs because
- 3.0 THREED.VBX does not the file type of THREED.VBX
- overwrite the Visual Basic changed from "APP" to "DLL"
- version 2.0 THREED.VBX. between version 2.0 and 3.0.
- SETUP.EXE now ignores file
- type differences and will
- install any file where the
- source and destination names
- are the same when the source
- file is the same or a newer
- version.
-
- 1.00.002 This error message: The error messages are now
- "Could not open or read "Error - Could not open file:
- file: <filename>" was <filename>" and "Error - Could
- replaced with two not read file: <filename>."
- separate error messages. Both errors cause SETUP.EXE to
- terminate.
-
- 1.00.002 New error message added: The new error message replaces:
- "Error - Insufficient "Error - Could not copy file:
- disk space on drive <source filename> ->
- <drive letter>:" This <destination filename>"
- error causes SETUP.EXE when there is insufficient
- to terminate. disk space.
-
- 1.00.002 Version information was The version number 1.00.002
- added to SETUP.EXE. was added to SETUP.EXE.
- Previous versions of SETUP.EXE
- have no version number.
-
- 1.00.003 Running SETUP.EXE This problem has been fixed so
- version 1.00.002 from a that you can run SETUP.EXE from
- subdirectory causes a subdirectory. SETUP.EXE
- "Error - Could not open provided with Visual Basic
- file: <path name> SETUP.LST version 3.0 does not have this
- problem.
-
- 1.00.003 VER.DL_ on distribution SETUP.EXE now copies VER.DL_
- disk does not copy over when the file/date time stamp of
- VER.DLL in destination the destination VER.DLL file is
- directory if the file date/ the same.
- time stamp is the same for
- both files.
-
- 1.00.004 A "Cannot copy file ..." SETUP.EXE no longer gives an
- error message occurs when error when the source file has
- attempting to copy a file an older version number than
- referenced in SETUP.LST that the destination file.
- has an older version number
- than the same file on the
- destination drive. This
- error causes SETUP.EXE to
- terminate.
-
- 1.00.004 SETUP.EXE copies over the SETUP.EXE no longer attempts to
- same or older version of copy VER.DLL if it is already in
- VER.DLL if it is in use use. It assumes that it can use
- by another application such an older version of VER.DLL if
- as File Manager. This can it exists and is in use.
- lead to a General Protection
- Fault (GP fault).
-